Automatic creation of graph time layer of model of computer network objects and relationships

ABSTRACT

A method and system create a model of a set of relationships between a set of parent computer network objects and a set of corresponding child computer network objects, over a period of time, and output a user interface graphing the model in a single view to illustrate the set of relationships over the period of time. The parent computer network objects include virtual machines and the child computer network objects include hosts. The user interface includes a search option to provide for a search of problems with the child computer network objects over the period of time.

RELATED APPLICATION

This application is a continuation of, and claims priority to, U.S.application Ser. No. 13/727,017, filed on Dec. 26, 2012, which is herebyincorporated by reference in its entirety.

FIELD

This description relates generally to graphs of service models showingthe relationships between computer network objects and the status ofeach object.

BACKGROUND

In a computer environment, a collection of equipment may providefunctionality, such as e-mail. The collection of equipment may include awhole network of computers and objects that work together. A diagram ofthat network may be referred to a service model. Operations graphs ofservice models can be very large and complex, especially when cloudcomputing objects and virtual objects are involved. These operationsgraphs may show the relationships between objects and the status of eachobject. An important type of relationship is an impacting relationship,which means that a child object can impact the status or health of aparent object. The child object supplies resources to the parent objectso the parent object can accomplish its tasks. If a child object goesdown, then the parent object is negatively affected. When an object isimpacted negatively by its child objects, an operations graph may showthis by changing the visual appearance of the relationship path betweenthe objects. For example if a child (such as a storage server) iscausing the parent (such as an e-mail server) to go critical, it changesa relationship indicator. The user can then see which child is causingthe parent to go critical.

The graph, however, is merely a snapshot of one moment in time andtherefore it only shows the current relationships and the current statusand causes. With the advent of virtual objects and cloud, however, anobject's children may change over time as resources are automaticallyshifted about to handle demand. An object's status may change fromred-green-red-green over time as a “bad” child moves in-out-in-out ofrelationship to the object. Therefore, if a user is trying to determinewhich child object is habitually causing problems for a parent object,the user must “catch” the graph before the “bad child” automaticallyshifts out from under the parent object.

In many cases, a problem can be much more complex than a single childcausing an issue. For example, there may be a unique combination ofcertain children causing one or more issues. A snapshot view of a graphdoes not make it easy to identify the causal patterns in such anenvironment. Accordingly, there exists a need for systems and methods toaddress the shortfalls of present technology and to provide other newand innovative features.

SUMMARY

Systems and methods described here provide users with across-timerelationship patterns in a graph view and the status effects of theserelationships over a span of time.

In various implementations, a method includes creating, by amicroprocessor of a computing device, a model of a set of relationshipsbetween a set of parent virtual machines and a corresponding set ofchild hosts, over a period of time, and displaying, on a display of thecomputing device, a user interface graphing the model in a single viewto illustrate the set of relationships over the period of time. Otherfeatures are contemplated. For example, a search option may be includedto provide for a search of issues with the child hosts in a specifictime frame.

In various implementations, a method includes creating, by amicroprocessor of a computing device, a model of a set of relationshipsbetween a set of parent computer network objects and a corresponding setof child computer network objects, over a period of time. A graph timelayer and a status of each of the set of relationships are displayed ona display of the computing device graphing the model. Each status may bedepicted at intervals over the period of time. A search option may bedisplayed to provide for a search of problems with the child computernetwork objects over the period of time.

Certain implementations include a system that may include a display, amemory including executable instructions, and a processor operablycoupled to the memory and configured to execute the executableinstructions to cause the system to

access a model of a set of relationships between a set of parent virtualmachines and a set of corresponding child hosts, over a period of time,and output on the display a user interface graphing the model in asingle view to illustrate the set of relationships over the period oftime and a status of each of the set of relationships. Each status maybe depicted at intervals over the period of time.

One or more of the implementations of the subject matter describedherein can be implemented so as to realize one or more of the followingadvantages. User has an easy way to see, in an integrated manner,relationships and causes over a span of time to look for casualpatterns, rather than memorizing each time point state and then mentallytrying to assemble a complete pattern of causal relationships over aspan of time. A user may see a big picture of how objects have behavedover time within one view rather than requiring the user to go todifferent views or different log files to assemble all of thisinformation.

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features will beapparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example graph of a parent and child object.

FIG. 2 is an example illustrating a graph time layer.

FIG. 3 is another example illustrating a graph time layer.

FIG. 4 is a flow chart illustrating an example method for providing agraph time layer.

FIG. 5 shows example or representative computing devices and associatedelements that may be used to implement systems and methods describedhere.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1 illustrates an example graph of a parent and child object. Asshown in the graph 100 of FIG. 1, parent object 110 and child object 120may be connected. Parent object 110 and child object 120 may be, forexample, computer network objects, services, servers, virtual machines,hosts, switches, routers, disk drives, applications, or other computerobjects. Child object 120 may supply resources to the parent object 110so the parent 110 object can accomplish its tasks. Parent object 110may, over time, receive sub-services from other child objects, such asthree different child objects (shown in graph 150). Over time, whichchild provides the sub-service changes. The graph 100 is a depiction ofa snapshot in time (e.g., 11:00 AM) of child object 120 providing aservice to parent object 110. The graph 150 is a depiction of fourdifferent snapshot views of providers and services over a period of timei.e., 12:00 PM, 12:15, 12:30, and 12:45 PM.

If the child object 110 experiences issues or goes down, then the parentobject 120 may be negatively affected. When parent object 120 isimpacted negatively by its child object 110, an operations graph mayshow this status by changing a visual appearance of a relationship path130 between the objects. For example, if a child object 120 is causingthe parent object 110 to go critical, an operations graph may change therelationship line 130 to be displayed in a certain color, such as red. Auser can then see which child is causing a parent object to go critical.

The parent object 120 and the child object 110 can communicate through anetwork, for example, an intranet or the Internet. While the parentobject 120 and the child object 110 are shown as two separate objects,in some implementations, the parent object 120 and the child object 110can be part of the same device or system.

In one example, a user may know that over the last hour the status of aservice, i.e., parent object 110, went into a warning status (which maybe depicted, in some examples, with a particular color such as yellow).The user also knows that the providers/children object of this servicechange over time. Yet, in merely looking at this snapshot shown in thegraph 100 of FIG. 1, the user can not what happened over time or whatcaused the warning status.

Graph 150 is a topology graph that illustrates, via the shading of theservice 160 and provider 153 at time 12:15 PM, that provider 153 causedthe service 160 to go to a warning status at 12:15 PM. It will beunderstood that such shading is for illustration purposes, and thatvarious color schemes, shading, designs, or other graphical userinterface elements may illustrate a warning or other status of aprovider, service, relationship, etc., at different points in time insuch a graph.

Yet, it is unclear from FIG. 1 why provider 153 automatically shiftedinto the provider role at 12:15 PM, or what was happening with providers151 or 152, or why there was a shift at 12:30 PM and another shift at12:45 PM. Thus, a graph with more detail over time is advantageous, andis shown in FIG. 2.

FIG. 2 illustrates an example graph time layer. Graph 200 may be shown,for example, when a user navigates an application or web page to aparent service of interest (e.g., ServiceX). Graph 200 includes a graphview 210, which includes a graphical user interface element 212 that mayrepresent a parent object, i.e., “ServiceX”. Other graphical userinterface elements may represent subservices or other parent or childobjects, such as subservice 214 and GoldWatch.com 216, and indicators ofhistorical changes, such as indicatory 218. Such elements may berepresented by different shapes or colors (e.g., yellow, green) toindicate, for example, various states or statuses of each object. As anexample, Goldwatch.com 216 may be a e-mail server and ServiceX 212 maybe a storage server that stores e-mails. If something goes wrong withServiceX212, the system may automatically switch to another storageserver.

A user may activate a “show time layer” function on this parent object.This can be done by any one of a number of activation methods associatedwith the graphical user interface element 212—e.g., a mouse click ofelement 212, a keyboard click, a right-click on a menu option, a toolbaricon selection, a swipe on a touch screen, etc. An activation of a “showtime layer” function is illustrated by the dashed line 213.

A time layer overlay 220 appears within the graph 200 view. Within thegraph view 210, the time layer 220 may be overlaid as a new layer in thegraph view 210, for example over the object selected, or may be a pop-upHTML or other window. The expanded view 250 shows how, in oneimplementation, a user may also open a layer to show both providers andconsumers. Each of the views shown in FIG. 2 may be illustrated usingvarious colors, shading, or other techniques to depict changes inrelationships, status of a relationship, warnings, or other aspects ofthe parent objects and child objects. The specific depiction and styleof graph view 210, time layer 220, and expanded view 250 are intendedfor illustration.

As shown in the graph view 210, a user may select graphical userinterface element 212 “serviceX” and in response to the user'sselection, time layer 220 is displayed. As discussed above, time layer220 may, in various implementations, be overlaid as a new layer in thegraph view 200, e.g., over the element 212 “serviceX”.

Time layer 220 may illustrate which subservices (e.g., database servers)were helping serviceX (e.g., an e-mail server) over a time span. Asshown in time layer 220, at time 12:00 PM: subservice 222 was theprovider and it was “green” as was the parent object, “serviceX” 212, asindicated by line 232. The color green may indicate an active status.Other indicators, colors, styles, lines, etc. may be used to indicate anactive status. Indicators such as arrows 233 may indicate a direction ofmovement from one object to another object to illustrate how arelationship between objects moves over time.

At time 12:15: subservice 222 failed (which may be indicated by a thinred line 234). Then, subservice 224 was already in a “red” state (whichmay be indicated by thin red line 236). Thus, subservice 226 took overthe provider role and it was in a “yellow” (i.e., warning) state asindicated by shaded line 238, but it was the most capable child objectat this point in time. The shading 235 of the interval from 12:15-12:30indicates that the entire serviceX was in a warning status during thattime interval.

At time 12:30: the provider role shifted to subservice 224 because itbecame “green” as indicated by line 240 (e.g., go or active state) andbecause subservice 226 was still in a “yellow” (i.e., warning) state asindicated by line 242.

At time 12:45: the provider shifted back to subservice 222 becausesubservice 224 went “red” as indicated by line 244 (i.e. inactivestate), and because subservice 226 also went “red” as indicated by line248 and because subservice 222 was “green” as indicated by line 246.Thin red lines, such as line 248, may indicate a relationship when achild object is not a causal impact for a parent object. Thick greenlines, such as line 246, may show the status of an active providerduring a time interval (e.g., provider 222 during the time interval from12:45-1:00) and a status of the provider impact (e.g., positive).

A time span (e.g., 12:00-1:00) may be selected or input by a user. Invarious implementations, selectable graphical user interface elements,such as arrow elements 270 and 272, may allow a user to shift a timespan being examined (e.g., from 12:00-1:00 to 2:00-3:00). Users may movethe time span using elements 270 or 272. Users may also start or stop orchange the time span duration, or adjust the length of intervalsdisplayed in a graph (e.g., increase from 15 minutes to 1 hourintervals).

In various implementations, users may apply a filter element 280, forexample to filter which children are shown, as well as the type ofrelationships and children shown. Users may also use filter element 280to filter a number of child layers shown to show depth of relationships.

In various implementations, users may also expand graph time layer 220to view 250, to show both the providers and consumers of an object(e.g., the object associated with element 212). For example, view 250illustrates that consumers 216 and 217 are consumers of “serviceX”represented by element 212.

It will be understood that the example illustrated in FIG. 2 isillustrative. More complex relationships between child objects andparent objects may exist. For example, in some cases, over time theremay be fifty different child objects and at any one time there may betwenty shifting relationships to the parent.

FIG. 3 is another example of a graph time layer. FIG. 3 includes graph300 and graph time layer 302. Graph 300 is another example illustratinghow a virtual machine (“VM”)-oriented objects graph may appear. Thegraph 300 illustrates why a VM switched hosts. As shown in graph 300,“VM5” 310 moved at time 10:30 because “hostA” 320 went to a criticalstatus, which may be indicated by a thin red line 322.

A user may view a graph time layer 302 of “hostB” 330, to show all theparent objects (which in this example are virtual machines) that “hostB”330 services, over the time period from 10:00 AM to 11:15 AM. A user mayview the graph time layer 302 by selecting an icon associated with“hostB” 330, or by selecting an option menu, with a key click, or byother activation options. As shown in graph time layer 302, “hostB” 330services “VM5” 310 from 10:30 AM to at 11:15 AM. The “hostB” 330 alsoservices “VM3” 340, “VM2” 342, and “VM1” 344 from 10:00 AM to 11:15 AM.The status of the service that “hostB” 330 provides to each virtualmachine may be illustrated by the color, shading, or thickness of theline(s) 350A, 250B, 350C, 350D, between “hostB” 330 and the virtualmachines. It will be understood that the specific depiction of lines350A, 350B, 350C, and 350D are for illustration, and that various othercolors, shapes, indicators, elements, etc. may be used to illustratestatus and relationship(s). Thus, a user may view the status of childobject “hostB” 330 and its relationship to various parent objects over aperiod of time.

As discussed above with respect to FIG. 2, the graph or graph timelayer(s) may include various elements such as color lines to indicatethe status of services, and selectable graphical user interface elementssuch as arrow elements 370 and 372, which may allow a user to shift atime span being examined. Users may move the time span start or stop orchange its duration size, or adjust intervals.

Other configurations and implementations are possible. For example, asdiscussed above with respect to FIG. 2, a size of the time frame shownmay be adjustable, such that a user may adjust a time frame from 30minutes to two hours, for example. A time frame may also be set bydefault or by a user. Further, the various intervals may also beadjusted by a user, for example from fifteen minute intervals to onehour intervals. Users may scroll through a time-elapsed view of thegraphs depicted in FIGS. 2 and 3 similar to a video player, usinganimation. Users may filter which children are shown, as well as thetype of relationships and children shown. Users may also filter a numberof child layers shown to show depth of relationships. For example, auser may wish to see two levels below a VM rather than only one layerand may expand a view to see two layers of child objects. User may alsohide or show different paths, for example to only view causalrelationships that affect a particular parent object, and avoid viewingother child objects. Users may multi-select top objects and look forcommon “bad” i.e., problem-causing children over time, to see patternsand remedy issues with the children. Users may select a “bad” child andexpand a view upward to see if there is another top level objectaffected by the bad child.

FIG. 4 a flow chart illustrating an example method for providing a graphtime layer. For convenience, the steps of the flow chart are describedwith reference to a system that performs the steps. The system can be,for example, a computing device described below with respect to FIG. 5,or other systems.

The system creates or accesses a model (e.g., a service model) of a setof relationships between a set of parent computer network objects and aset of corresponding child computer network objects, over a period oftime (410). The system may, in some implementations, access a model thathas been created and stored at a remote server or other computingdevice. The model may be created based on data acquired or aggregated bythe computing device or by one or more servers associated with the setof parent computer network objects and the set of corresponding childcomputer network objects. The data includes statuses of eachrelationship between a child object and parent object such as thosedescribed above with respect to FIGS. 2 and 3, and the status changesover any time period. The collection and aggregation of such data may beautomatically and continually updated by the computing device or by theserver(s). In various implementations, the model and all associated data(e.g., statuses, history of relationship changes, etc.) may be stored byone or more servers and accessed by one or more computing devices.

The system displays a user interface graphing the model and a status ofeach of the set of relationships, where each status is depicted atintervals over the period of time (420). For example, the user interfacemay include the graph views depicted in FIGS. 2 and 3. The system mayoptionally display a search option to provide for a search of commoncomputer network objects over the period of time (430). Such a searchoption may include a drop down menu, searchable tool bar(s), an HTMLform with filters, or other options.

FIG. 5 is a block diagram showing example or representative computingdevices and associated elements that may be used to implement systemsand methods described here. Computing device 500 is intended torepresent various forms of digital computers, such as laptops, desktops,workstations, personal digital assistants, servers, blade servers,mainframes, and other appropriate computers. Computing device 550 isintended to represent various forms of mobile devices, such as personaldigital assistants, cellular telephones, smart phones, and other similarcomputing devices. The components shown here, their connections andrelationships, and their functions, are meant to be exemplary only, andare not meant to limit implementations of the inventions describedand/or claimed in this document.

Computing device 500 includes a processor 502, memory 504, a storagedevice 506, a high-speed interface 508 connecting to memory 504 andhigh-speed expansion ports 510, and a low speed interface 512 connectingto low speed bus 514 and storage device 506. Each of the components 502,504, 506, 508, 510, and 512, are interconnected using various busses,and may be mounted on a common motherboard or in other manners asappropriate. The processor 502 can process instructions for executionwithin the computing device 500, including instructions stored in thememory 504 or on the storage device 506 to display graphical informationfor a GUI on an external input/output device, such as display 516coupled to high speed interface 508. In other implementations, multipleprocessors and/or multiple buses may be used, as appropriate, along withmultiple memories and types of memory. Also, multiple computing devices500 may be connected, with each device providing portions of thenecessary operations (e.g., as a server bank, a group of blade servers,or a multi-processor system).

The memory 504 stores information within the computing device 500. Inone implementation, the memory 504 is a volatile memory unit or units.In another implementation, the memory 504 is a non-volatile memory unitor units. The memory 504 may also be another form of computer-readablemedium, such as a magnetic or optical disk.

The storage device 506 is capable of providing mass storage for thecomputing device 500. In one implementation, the storage device 506 maybe or contain a computer-readable medium, such as a floppy disk device,a hard disk device, an optical disk device, or a tape device, a flashmemory or other similar solid state memory device, or an array ofdevices, including devices in a storage area network or otherconfigurations. A computer program product can be tangibly embodied inan information carrier. The computer program product may also containinstructions that, when executed, perform one or more methods, such asthose described above. The information carrier is a computer- ormachine-readable medium, such as the memory 504, the storage device 506,or memory on processor 502.

The high speed controller 508 manages bandwidth-intensive operations forthe computing device 500, while the low speed controller 512 manageslower bandwidth-intensive operations. Such allocation of functions isexemplary only. In one implementation, the high-speed controller 508 iscoupled to memory 504, display 516 (e.g., through a graphics processoror accelerator), and to high-speed expansion ports 510, which may acceptvarious expansion cards (not shown). In the implementation, low-speedcontroller 512 is coupled to storage device 506 and low-speed expansionport 514. The low-speed expansion port, which may include variouscommunication ports (e.g., USB, BLUETOOTH, ETHERNET, wireless ETHERNET)may be coupled to one or more input/output devices, such as a keyboard,a pointing device, a scanner, or a networking device such as a switch orrouter, e.g., through a network adapter.

The computing device 500 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as astandard server 520, or multiple times in a group of such servers. Itmay also be implemented as part of a rack server system 524. Inaddition, it may be implemented in a personal computer such as a laptopcomputer 522. Alternatively, components from computing device 500 may becombined with other components in a mobile device (not shown), such asdevice 550. Each of such devices may contain one or more of computingdevice 500, 550, and an entire system may be made up of multiplecomputing devices 500, 550 communicating with each other.

Computing device 550 includes a processor 552, memory 564, aninput/output device such as a display 554, a communication interface566, and a transceiver 568, among other components. The device 550 mayalso be provided with a storage device, such as a microdrive or otherdevice, to provide additional storage. Each of the components 550, 552,564, 554, 566, and 568, are interconnected using various buses, andseveral of the components may be mounted on a common motherboard or inother manners as appropriate.

The processor 552 can execute instructions within the computing device550, including instructions stored in the memory 564. The processor maybe implemented as a chipset of chips that include separate and multipleanalog and digital processors. The processor may provide, for example,for coordination of the other components of the device 550, such ascontrol of user interfaces, applications run by device 550, and wirelesscommunication by device 550.

Processor 552 may communicate with a user through control interface 558and display interface 556 coupled to a display 554. The display 554 maybe, for example, a TFT LCD (Thin-Film-Transistor Liquid Crystal Display)or an OLED (Organic Light Emitting Diode) display, or other appropriatedisplay technology. The display interface 556 may comprise appropriatecircuitry for driving the display 554 to present graphical and otherinformation to a user. The control interface 558 may receive commandsfrom a user and convert them for submission to the processor 552. Inaddition, an external interface 562 may be provide in communication withprocessor 552, so as to enable near area communication of device 550with other devices. External interface 562 may provide, for example, forwired communication in some implementations, or for wirelesscommunication in other implementations, and multiple interfaces may alsobe used.

The memory 564 stores information within the computing device 550. Thememory 564 can be implemented as one or more of a computer-readablemedium or media, a volatile memory unit or units, or a non-volatilememory unit or units. Expansion memory 574 may also be provided andconnected to device 550 through expansion interface 572, which mayinclude, for example, a SIMM (Single In Line Memory Module) cardinterface. Such expansion memory 574 may provide extra storage space fordevice 550, or may also store applications or other information fordevice 550. Specifically, expansion memory 574 may include instructionsto carry out or supplement the processes described above, and mayinclude secure information also. Thus, for example, expansion memory 574may be provide as a security module for device 550, and may beprogrammed with instructions that permit secure use of device 550. Inaddition, secure applications may be provided via the SIMM cards, alongwith additional information, such as placing identifying information onthe SIMM card in a non-hackable manner.

The memory may include, for example, flash memory and/or NVRAM memory,as discussed below. In one implementation, a computer program product istangibly embodied in an information carrier. The computer programproduct contains instructions that, when executed, perform one or moremethods, such as those described above. The information carrier is acomputer- or machine-readable medium, such as the memory 564, expansionmemory 574, or memory on processor 552, which may be received, forexample, over transceiver 568 or external interface 562.

Device 550 may communicate wirelessly through communication interface566, which may include digital signal processing circuitry wherenecessary. Communication interface 566 may provide for communicationsunder various modes or protocols, such as GSM voice calls, SMS, EMS, orMMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others.Such communication may occur, for example, through radio-frequencytransceiver 568. In addition, short-range communication may occur, suchas using a BLUETOOTH, WiFi, or other such transceiver (not shown). Inaddition, GPS (Global Positioning System) receiver module 570 mayprovide additional navigation- and location-related wireless data todevice 550, which may be used as appropriate by applications running ondevice 550.

Device 550 may also communicate audibly using audio codec 560, which mayreceive spoken information from a user and convert it to usable digitalinformation. Audio codec 560 may likewise generate audible sound for auser, such as through a speaker, e.g., in a handset of device 550. Suchsound may include sound from voice telephone calls, may include recordedsound (e.g., voice messages, music files, etc.) and may also includesound generated by applications operating on device 550.

The computing device 550 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as acellular telephone 580. It may also be implemented as part of a smartphone 582, personal digital assistant, or other similar mobile device.

Various implementations of the systems and techniques described here canbe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations can include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor, and can be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. As used herein, the terms “machine-readable medium” or“computer-readable medium” refer to any computer program product,apparatus and/or device (e.g., magnetic discs, optical disks, memory,Programmable Logic Devices (PLDs)) used to provide machine instructionsand/or data to a programmable processor, including a machine-readablemedium that receives machine instructions as a machine-readable signal.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniquesdescribed here can be implemented on a computer having a display device(e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor)for displaying information to the user and a keyboard and a pointingdevice (e.g., a mouse or a trackball) by which the user can provideinput to the computer. Other kinds of devices can be used to provide forinteraction with a user as well; for example, feedback provided to theuser can be any form of sensory feedback (e.g., visual feedback,auditory feedback, or tactile feedback); and input from the user can bereceived in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in acomputing system that includes a back end component (e.g., as a dataserver), or that includes a middleware component (e.g., an applicationserver), or that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components. The components of the system can be interconnectedby any form or medium of digital data communication (e.g., acommunication network). Examples of communication networks include alocal area network (“LAN”), a wide area network (“WAN”), and theInternet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

A number of implementations have been described. Nevertheless, variousmodifications may be made without departing from the spirit and scope ofthe invention. In addition, the logic flows depicted in the figures donot require the particular order shown, or sequential order, to achievedesirable results. In addition, other steps may be provided, or stepsmay be eliminated, from the described flows, and other components may beadded to, or removed from, the described systems. Accordingly, otherimplementations are within the scope of the following claims.

What is claimed is:
 1. A method comprising: creating, by amicroprocessor of a computing device, a model of a set of relationshipsthat includes virtual machines, over a time period; and displayinghistorical data, on a display of the computing device, in a userinterface graphing the model in a single view to illustrate changes inthe set of relationships between a user-selected first and second timeperiod, the view including changes in status corresponding to one ormore virtual machines with a warning status or a critical status.
 2. Themethod of claim 1, wherein the user interface enables changes to a timespan duration for displaying historical data to scale from a firstinterval to a second interval.
 3. The method of claim 2, wherein thefirst interval is measured in hours and the second interval is measuredin minutes.
 4. The method of claim 1, further comprising: generating astatus indication for a relationship between virtual machines and childhosts.
 5. The method of claim 1, wherein the first and second timeperiods are adjustable.
 6. The method of claim 1, wherein a time elapsedview is used to display historical data.
 7. The method of claim 1,further comprising: filtering which virtual machines are displayed. 8.The method of claim 1, further comprising: filtering which of the set ofrelationships are displayed.
 9. The method of claim 1, furthercomprising: displaying a search option.
 10. A system comprising: adisplay; a memory including executable instructions; and a processoroperably coupled to the memory and configured to execute the executableinstructions to cause the system to: create, by a microprocessor of acomputing device, a model of a set of relationships that includesvirtual machines, over a time period; and display historical data, onthe display of the computing device, in a user interface graphing themodel in a single view to illustrate changes in the set of relationshipsbetween a user-selected first and second time period, the view includinga status change indicator corresponding to one or more virtual machineswith a warning status or a critical status.
 11. The system of claim 10,wherein the user interface enables changes to a time span duration fordisplaying historical data to scale from a first interval to a secondinterval.
 12. The system of claim 11, wherein the first interval ismeasured in hours and the second interval is measured in minutes. 13.The system of claim 10, wherein the processor is further configured toexecute the instructions to cause the system to: generate a statusindication for a relationship between virtual machines and child hosts.14. The system of claim 10, wherein the first and the second timeperiods are adjustable.
 15. The system of claim 10, wherein a timeelapsed view is used to display historical data.
 16. The system of claim10, wherein the processor is further configured to execute theinstructions to cause the system to: filter which virtual machines aredisplayed.
 17. The system of claim 10, wherein the processor is furtherconfigured to execute the instructions to cause the system to: filterwhich of the set of relationships are displayed.
 18. The system of claim10, wherein the processor is further configured to execute theinstructions to cause the system to: display a search option.
 19. Anon-transitory computer-readable storage medium including code segmentsthat when executed by a processor cause the processor to: create, by amicroprocessor of a computing device, a model of a set of relationshipsthat includes virtual machines, over a time period; and displayhistorical data, on a display of the computing device, in a userinterface graphing the model in a single view to illustrate changes inthe set of relationships between a user-selected first and second timeperiod, the view including changes in status corresponding to one ormore virtual machines with a warning status or a critical status. 20.The non-transitory computer-readable storage medium of claim 19, whereinthe user interface enables changes to a time span duration fordisplaying historical data to scale from a first interval to a secondinterval.
 21. The non-transitory computer-readable storage medium ofclaim 20, wherein the first interval is measured in hours and the secondinterval is measured in minutes.